Unable to push my commit with Git

[remoteconn-7891]

Select Topic Area

Question

Body

Hello, I'm not able to push my most recent commit via Git to my remote repo. I'm using my Ubuntu local terminal.

There are no errors when running git add ., git commit -m "". But when I write the command git push origin master I get this error message

Enumerating objects: 12, done.
Counting objects: 100% (12/12), done.
Delta compression using up to 4 threads
Compressing objects: 100% (7/7), done.
Writing objects: 100% (8/8), 930.59 MiB | 1.29 MiB/s, done.
Total 8 (delta 4), reused 1 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (4/4), completed with 4 local objects.
remote: error: Trace: 313005b0b275b41578b155eada66dd4422681d8cd80a4017c095e4bde513cd07
remote: error: See https://gh.io/lfs for more information.
remote: error: File kibana-8.17.4-amd64.deb is 327.03 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: File elasticsearch-8.17.4-amd64.deb is 606.95 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.
To github.com:remoteconn-7891/MyProject.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'github.com:remoteconn-7891/MyProject.git'

How do I go about fixing this?

[AMRYB]

Hey there 👋
The issue you're facing happens because you're trying to push files that exceed GitHub's maximum file size limit (100MB). Specifically, these two .deb files are too large:

• kibana-8.17.4-amd64.deb – 327 MB
• elasticsearch-8.17.4-amd64.deb – 606 MB

GitHub doesn't allow pushing files over 100MB, which is why you're getting that error.

✅ How to fix it:

1. Use Git LFS (Large File Storage)

This is the official way to handle large files on GitHub:

1. Install Git LFS:

   sudo apt install git-lfs

2. Initialize Git LFS in your repo:

   git lfs install

3. Track your large files:

   git lfs track "*.deb"

4. Re-add the files so LFS tracks them:

   git add .gitattributes
   git add kibana-8.17.4-amd64.deb elasticsearch-8.17.4-amd64.deb
   git commit -m "Track large files with Git LFS"

5. Then push again:

   git push origin master

---

⚠️ Alternative Option: Don't Push Large Files to GitHub

If you don't need to store the .deb files in the repo, it's better to:

• Remove them from the commit:

  git rm --cached kibana-8.17.4-amd64.deb elasticsearch-8.17.4-amd64.deb
  git commit -m "Remove large files"
  git push origin master

• And store those files elsewhere, like Dropbox, Google Drive, or a private server.

[AMRYB]

Sometimes

[remoteconn-7891]

Shit same error again

Enumerating objects: 13, done.
Counting objects: 100% (13/13), done.
Delta compression using up to 4 threads
Compressing objects: 100% (7/7), done.
Writing objects: 100% (9/9), 326.07 MiB | 1.28 MiB/s, done.
Total 9 (delta 5), reused 6 (delta 2), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (5/5), completed with 4 local objects.
remote: error: Trace: f93c5a86cf817fd75d0ccb45aeace013af7157e1224d9d66dd4356f8ebcf3fca
remote: error: See https://gh.io/lfs for more information.
remote: error: File kibana-8.17.4-amd64.deb.1 is 327.03 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.
To github.com:remoteconn-7891/MyProject.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'github.com:remoteconn-7891/MyProject.git'

[AMRYB]

Create a New Clean Repo (RECOMMENDED)

Since you don’t need the old Git history:

1. In your project folder, wipe Git history:

   rm -rf .git

2. Re-init the repo:

   git init
   git remote add origin https://github.com/YOUR_USERNAME/YOUR_NEW_REPO.git

3. Make sure the .deb files are NOT there. Delete or .gitignore them.

4. Add, commit, and push:

   git add .
   git commit -m "Clean initial commit"
   git push -u origin master

---

If this finally works, it was fixed by me.
If not… I’ve officially lost all hope. 😩

[remoteconn-7891]

Finally got it working, had to use Copilot as an absolutely last resort. I hate using LLM for my projects

[AMRYB]

Glad you got it working — even if Copilot had to jump in at the last minute 😅 Also, if my reply helped, would be awesome if you could mark it as the answer so others can find it too!

[mecodeatlas]

Welcome to the GitHub Community, @remoteconn-7891, we're happy you're here! You are more likely to get a useful response if you are posting your question in the applicable category and are explicit about what your project entails--giving a few more details might help someone give you a nudge in the right direction. I've gone ahead and moved it for you. Good luck!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬